Device and vehicle pairing using a network connection

ABSTRACT

Examples of the present disclosure relate to a device, method, and medium storing instructions for execution by a processor for refreshing memory blocks of solid state memory through a temperature compensated refresh rate. Techniques discussed herein include a solid state memory to store data and a temperature sensor to identify a temperature of the solid state memory. The memory device with solid state memory also includes a memory controller that periodically refreshes memory blocks of the solid state memory at an adjustable refresh rate, wherein memory controller is to adjust the adjustable refresh rate based on the temperature of the solid state memory.

CROSS-REFERENCED TO RELATED APPLICATIONS

This application claims benefit of U.S. Provisional Application No.62/711,877 filed on Jul. 30, 2018, which the disclosure of which ishereby incorporated by reference in its entirety for all purposes.

FIELD OF THE INVENTION

The present disclosure generally relates to a method, system, and devicefor paring a device and vehicle for direct communications using aseparate network connection. More specifically, the present disclosurerelates to providing communication connection information over a networkconnection that enables communication between two or more devices. In anexample, the two devices can be a car and smartphone directly using adifferent communication protocol than the way the connection informationwas sent.

BACKGROUND

This section is intended to introduce the reader to various aspects ofart, which may be related to various aspects of the present disclosure,which are described and/or claimed below. This discussion is believed tobe helpful in providing the reader with background information tofacilitate a better understanding of the various aspects of the presentdisclosure. Accordingly, it can be understood that these statements areto be read in this light, and not as admissions of prior art.

Vehicles may include electronic components that interconnect with thevehicle itself as well as component systems such as navigation systems,audio systems, and media systems. A vehicle may include a networkingcomponent that can connect to the internet or other devices throughdirect pairing to the device based on commands initiated at both thedevice and the vehicle indicating they are ready to pair followed by auser action confirming that a particular pairing is approved.

SUMMARY

Generally, the techniques herein include a server device for pairing aconnecting device and vehicle using a network connection. The serverdevice can include a memory to store data and instructions, a processor,and a vehicle identification number (VIN) stored in the memory, wherethe VIN is associated with connection information for a vehicleassociated with the VIN. The server device also includes a VIN matcherstored in the memory that when executed by the processor denies arequest for connection information in response to a mismatch between asupplied VIN from a connecting device and the VIN stored in memory. Thememory of the server device also includes a server device networkconnector stored in the memory that when executed by the processor sendsthe connection information to a connecting device in response to a matchbetween the supplied VIN from the connecting device and the VIN storedin memory. In an example, the connection information is sent through anetwork connection. The network connection may use a first communicationprotocol. The connection information sent may contains information forthe connecting device to connect to the vehicle. The connectioninformation used to connect the device to the vehicle may use a secondseparate second communication protocol that doesn't use the networkconnection.

A method for pairing a device and vehicle using a network connectionincluding identifying a vehicle identification number (VIN) andconnection information, wherein the VIN stored in a memory device thatlinks the VIN with the connection information. The method also includesattempting to match a supplied VIN from a connecting device with the VINstored in the memory device. The method further includes sending theconnection information to the connecting device in response to thesupplied VIN matching the VIN stored in the memory device, wherein theconnection information connects the connecting device to the vehiclewithout an intermediate processor between the connecting device and thevehicle.

The techniques disclosed herein further include a tangible,non-transitory, computer-readable medium comprising instructions that,when executed by a processor, pairs a device and a vehicle using anetwork connection. In an example, the instructions stored in thecomputer-readable medium can execute on a processor to store a vehicleidentification number (VIN) and connection information in thecomputer-readable medium, wherein the memory device associates the VINwith the connection information and a request with the VIN returns theconnection information. In an example, the instructions stored in thecomputer-readable medium can execute on a processor to attempt to matcha supplied VIN from a connecting device through a network connection tothe computer-readable medium, where the matching is attempted betweenthe supplied VIN and the VIN stored in the computer-readable medium. Inan example, the instructions stored in the computer-readable medium canexecute on a processor to send the connection information to theconnecting device in response to the supplied VIN matching the VINstored in the computer-readable medium, wherein the connectioninformation sent connects the connecting device to the vehicle withoutan intermediate server between the connecting device and the vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-mentioned and other features and advantages of the presentdisclosure, and the manner of attaining them, may become apparent and bebetter understood by reference to the following description of oneexample of the disclosure in conjunction with the accompanying drawings,where:

FIG. 1 is a block diagram of an example system for pairing a device anda vehicle using a network connection;

FIG. 2 is a block diagram of an example vehicle in a system for pairinga device and a vehicle using a network connection;

FIG. 3 is a block diagram of an example device in a system for pairing adevice and a vehicle using a network connection;

FIG. 4 is a process flow diagram of an example method for pairing adevice and a vehicle using a network connection; and

FIG. 5 is a block diagram of an example computer-readable medium storinginstructions, that when executed on a processor pairs a device and avehicle using a network connection.

Correlating reference characters indicate correlating parts throughoutthe several views. The exemplifications set out herein illustrateexamples of the disclosure, in one form, and such exemplifications arenot to be construed as limiting in any manner the scope of thedisclosure.

DETAILED DESCRIPTION OF EXAMPLES

One or more specific examples of the present disclosure are describedbelow. In an effort to provide a concise description of these examples,not all features of an actual implementation are described in thespecification. It can be appreciated that in the development of any suchactual implementation, as in any engineering or design project, numerousimplementation-specific decisions may be made to achieve the developers'specific goals, such as compliance with system-related andbusiness-related constraints, which may vary from one implementation toanother. Moreover, it can be appreciated that such a development effortmight be complex and time consuming, and is a routine undertaking ofdesign, fabrication, and manufacture for those of ordinary skill havingthe benefit of this disclosure.

The present disclosure describes a pairing of devices using data from anetwork connection. More specifically, several different variations aredescribed herein where a vehicle is paired with a device using data froma first connection type or protocol, where the pairing communicationonce paired varies from the first connection type. In an example, thedevice and vehicle may pair initially negotiating secure connectionsthrough a direct WiFi connection or a cellular data network, such as aLong-Term Evolution (LTE) connection and then transition into only usingBluetooth. In the present disclosure, the information that provides thename of the vehicle access point is not manually input by a user butinstead previously provided through a server to the connecting device.Thus a user may not need to take any action for the pairing of theirdevice when actually getting in or approaching their vehicle even forthe first time as the information has already be provided to theirdevice through an internet connection. In an example, this connectinginformation, such as an access point SSID of the vehicle as well as anSSID authentication code can be associated in a server to the vehicleidentification number (VIN) of the vehicle. Once a vehicle is purchased,the VIN may be input to the device and the connection informationretrieved from the server device. Using this connection information, theconnecting device may then access the vehicle and begin device-to-devicepairing protocols through the connection enabled by the connectioninformation. In an example, the connection information is provided tothe device through network connection that is distinct from the protocolor communication style used for the pairing of the device to thevehicle. A pairing of devices may involve communication with nointermediate processor, server, or network, while the network connectionmay include an intermediate server, processor, storage, or network.Accordingly, the initial set up of a vehicle to device pairing may beconsidered out-of-band from the final pairing configuration. Further andmore complete details are outlined in the Figures below.

FIG. 1 is a block diagram of an example system 100 for pairing a deviceand a vehicle using a network connection. The lines used to connectvarious components do not necessary connect to the exact componentthrough electrical leads, but instead are shown here to indicate ageneral pathway and flow of communication.

The example system can include a server 102 that enables pairing betweena vehicle 104 and a device 106. As used herein, the server 102 may be ahardware device remotely located from both the vehicle and the device.The server 102 may include digital storage space and an organizationalsystem that can store a large amount of information about the vehicle104 or a plurality of vehicles. The vehicle 104 may connect to theserver 102 using a vehicle-to-server network connection 108. The vehiclemay provide information about the vehicle to the server 102. The server102 may connect to the device using a server-to-device networkconnection 108. In an example, both network connections include a serverbetween the two communicating devices. The timing of the communicationbetween the vehicle 104, server 102, and device 106 can vary based on anumber of circumstances. In an example, the vehicle provides a vehicleidentification number (VIN) as well as access point information to awireless component installed on the vehicle. The providing of a VIN andaccess point information to the server through the vehicle-to-servernetwork connection 108 can occur at the time of installation of theaccess point into the vehicle 104. The server to device networkconnection 110 can provide the access point information in response tothe device 106 providing a VIN that matches to access point informationstored in the server 102.

In an example, the device 106 may provide a VIN in response to thedevice 106 being within a threshold distance of the vehicle. Otherexamples include the device 106 providing a VIN in response to start-upof the device, in response to a user action, or when a user,manufacturer, or other vehicle seller provides the VIN information orother corresponding information to the device 104 upon purchase of thevehicle.

Once a device has received the connecting information from the server102, the device may then attempt pairing communications 112 with thevehicle 104 directly. As used herein the term pairing refers to a directdevice to device communication without an intermediate server, relay,router, switch, base station of cellular communications, processor, orother hardware device. In an example, the pairing communications 112 areestablished following a handshake protocol for secure communicationsthat follow known standards of pairing communications. Pairingcommunications 112 can be through Bluetooth, Wi-Fi, or other device todevice communications.

In an example, the server 102 may provide the device 106 withinformation about the access point name of the vehicle 104. The device106 may then initiate pairing communications 112 by initiating an accessrequest using WiFi and the access point provided through the server todevice network connection 110. In this way, the initial access to thevehicle may be considered obtained through an out-of-band communication.The pairing communications 112 may use a different protocol than thenetwork communications from which the device 106 received theinformation for initiating the pairing communications. In an example,while an access point for the vehicle 104 may be provided to the device106 over a server to device network connection 110 following an acellular data network protocols, such as LTE cellular communicationsprotocols, the pairing communications may be initiated following WiFiprotocols.

The vehicle 104 can include a vehicle network connector 114. The device106 can include a device network connector. The vehicle networkconnector 114 and the device network connector 116 can be networkinterface controllers for wireless communications with the server 102.Each of the vehicle network connector 114 and the device networkconnector 116 can be a network interface card, network adapter, orphysical network interface. The vehicle network connector 114 and devicenetwork connector 116 are located in the vehicle 104 and the device 106,respectively, and can each include a network controller that implementsthe electronic circuitry required to communicate using a specificphysical layer and data link layer standard such as Wi-Fi or a cellulardata network, such as LTE. The vehicle network connector 114 maycommunicate with the server 102 through the vehicle-to-server networkconnection 108 as described herein. The device network connector 116 maycommunicate with the server 102 through the server to device networkconnection 110 as described herein.

The vehicle 104 can include a vehicle to device connector 118 and thedevice 106 can include a device to vehicle connector 120. The device 106can include a device to vehicle connector 120. The vehicle to deviceconnector 118 and the device to vehicle connector 120 can be pairinghardware that communicate directly with one another. In an example,pairing communications 112 can be initiated between the vehicle todevice connector 118 and the device to vehicle connector 120. In anexample, the vehicle to device connector 118 and the device to vehicleconnector 120 may follow a Bluetooth protocol for establishing securecommunications including a handshake sequence. In an example, thehandshake sequence can be negotiated per Bluetooth out of band protocolsfollowing 802.11 standards using a mutually authenticated transportsecurity layer between the vehicle 104 and the device 106.

The server 102 can orchestrate the exchange of connection information.The vehicle 104 may provide information to a server 102 indicating how adevice 106 may initiate communication with the vehicle 104. In anexample, the vehicle 104 may provide information about the digitaladdress and access credential for the vehicle to device connector 112 tothe server along with a VIN identifying the vehicle. The server 102 maystore the VIN of a vehicle or a number of vehicles as well as theirassociated connection information. The server 102 may provide theconnection information to a device 106 either through a push of thisinformation or in response to a request for the connection informationfrom the device 106. In an example, the device 106 may supply a VIN tothe server 102. The server 102 may include a VIN matcher 122 to attemptto match the supplied VIN to a VIN stored in the server 102. If a VINmatcher 122 identifies a matching VIN in the server 102, then the serverdevice network connector 124 may transmit the connection informationassociated with the supplied VIN to the device 106. Based on theconnection information, the device 106 may initiate communications withthe vehicle 104 specifically through pairing communications 112 asdescribed herein.

FIG. 2 is a block diagram of an example vehicle in a system for pairinga device and a vehicle using a network connection. Like numbered itemsare as described with respect to FIG. 1.

The vehicle network connector 114 may be a separate component installedin the vehicle 104 during manufacturing or assembly of the vehicle 104.The vehicle network connector may include a generated server address202. As used herein, the generated server address 202 may include usingbuilt in a cellular data network modem, such as an LTE modem followingthe standards of LTE communication. In an example, the generated serveraddress 202 may also be any other identifier to allow pairingcommunications with the vehicle 104. As disclosed herein, pairingcommunications refer to communications that do not go through a centralnetwork or server and are device to device such as an ID generated asthe name of a WiFi access point following the standards of WiFiprotocol. Accordingly, the providing of the generated server address 202from the vehicle to a server is to enable pairing communicationsdirectly with the vehicle 104 from a device.

The vehicle network connector 114 can also include a generatedauthentication certificate 204. This authentication certificate may beused to gain access to the vehicle to device connector 118 by validatingthe device attempting access is authorized to communicate with thevehicle. The vehicle network connector 114 may communicate the generatedserver address 202, the generated authentication certificate 204, andthe vehicle identification number (VIN) 206 to a server. When sendingthe generated server address 202, the generated authenticationcertificate 204, and the VIN 206 to a server all at once, the VIN 206may be associated with the generated server address 202 and thegenerated authentication certificate 204 such that these elements arestored in a look-up table, associative array, or other storageconfiguration where a request using a VIN 206 can find and retrieve thegenerated server address 202 and the generated authenticationcertificate 204.

The vehicle to device connector 118 can include a vehicle to deviceprotocol negotiator 210. Once a device has a generated server address202 and the generated authentication certificate 204, the device mayattempt to access the vehicle 104 wirelessly by contacting the vehicleto device connector 118. The vehicle to device protocol negotiator 210may handle the establishment of a secure connection following anestablished digital communication protocol. In an example, the vehicleto device protocol negotiator 210 may follow the pairing protocol forBluetooth secure communications between devices. In an example, theVehicle to Device Connector 118 may use a WiFi access point of thevehicle for direct communications initiated by the device. Incircumstances where the vehicle is using the WiFi Access point, then theVehicle to Device connector may provide an SSID and SSID authenticationkey for validation with the personal device.

In an example, negotiation through a vehicle to device protocolnegotiator 210 can include negotiating a Bluetooth out of bandconnection following the IEEE 802.11 standard using mutuallyauthenticated transport layer security. In various alternatives, thenegotiation of a vehicle to device protocol negotiator 210 can useSecure Bluetooth (BT) Classic Out of Band (OOB) pairing protocols,Secure Bluetooth Low Energy (BLE) OOB Pairing protocols, Legacy BLE OOBpairing, or any other suitable device to device protocols. In oneexample, following one protocol, the vehicle to device protocolnegotiator 208 can provide through pairing communications a Bluetoothmedia access control (MAC) address, Mrand, 128-bit temporary key (TK),and a pairing response command. The vehicle to device protocolnegotiator 210 can also receive and store from a device the device's ownBluetooth MAC address, Srand, 128 bit TK, and a pairing request command.Using the received information, the vehicle to device protocolnegotiator 210 may calculate Mconfirm, provide Mconfirm back to thedevice, and receive a calculated Sconfirm from the device whilecalculating a vehicle Sconfirm value and attempting to match thereceived Sconfirm from the device as well as the calculated Sconfirm inthe vehicle. In response to a value match between the received andcalculated Sconfirm values, the vehicle to device protocol negotiator210 may complete the pairing for secure communication between the deviceand the vehicle.

In another example, a vehicle and device may authenticate each otherprior to being within pairing communication range. When the device is afurther physical distance from the pairing communications with thevehicle, the vehicle to device protocol negotiator 210 may also attemptto authorize and validate pairing communications through a networkcommunication path. In this example, the vehicle to device protocolnegotiator 210 may provide and receive validation and credentialsthrough a server. In this example, the vehicle to device protocolnegotiator 210 may provide through the network communications aBluetooth media access control (MAC) address, Mrand, 128-bit temporarykey (TK), and a pairing response command to enable later authenticatedand secure pairing when the device enters a threshold physical proximityenabling pairing communications.

The vehicle to device protocol negotiator 210 can also receive and storefrom a device communicating, through the network connection, thedevice's own Bluetooth MAC address, Stand, 128 bit TK, and a pairingrequest command. Using the received information, the vehicle to deviceprotocol negotiator 210 may calculate Mconfirm, provide Mconfirm back tothe device through the network communications with a server, and receivea calculated Sconfirm from the device through the network communicationswith a server. The vehicle to device protocol negotiator 201 may furthercalculate a vehicle Sconfirm value and attempt to match the receivedSconfim from the device and the calculated Sconfirm in the vehicle. Inresponse to a value match between the received and calculated Sconfirmvalues, the vehicle to device protocol negotiator 210 may complete theauthorization for pairing for secure communication between the deviceand the vehicle that will become active when the device enters aphysical proximity that enables pairing communication. The above valuesand names of protocol negotiation may vary based on the protocol used.

FIG. 3 is a block diagram of an example device in a system for pairing adevice and a vehicle using a network connection. Like numbered items areas described with respect to FIG. 1.

The device network connector 116 may receive and/or store an input VIN302. In an example, the input VIN 302 may be input by a user or providedthrough another device through email, electronic communications, digitalphotograph with scanned and detected numbering in the photograph,transmitted through near field communications (NFC), or other suitablemeans of a VIN being input to a device 106. The device network connector116 may also include a received server address 304 and a receivedauthentication certificates 306 for communications through a cellulardata network, such as LTE. Both the received server address 304 and thereceived authentication certificates 306 can be received through networkconnections. In an example, the input VIN 302 may be provided to aserver through network communications and the server address 304 andauthentication certificates 306 may be received by the device networkconnector in response to a match of VIN at the server. While this figureshows communication of a server address through cellular data networkcommunication protocols, such as LTE, other communication protocols arepossible including WiFi.

The device to vehicle connector 120 may include a device to vehicleprotocol negotiator to use the received server address 304 and thereceived authentication certificates 306 to access a vehicle throughpairing communications. As discussed herein, pairing communications mayavoid digital, wired, electronic, or other similar communicationsthrough a network, router, switch or other intermediate hardware betweenthe device 106 and the vehicle. The device to vehicle protocolnegotiator 308 may access a vehicle access point using the receivedserver address 304 and the received authentication certificates 306 inorder to initiate and negotiate further pairing communications through aWiFi, Bluetooth, or other protocol that may differ from the protocolused for the network communications with a server. In an example, theDevice to Vehicle Connector 120 may use a WiFi access point of thevehicle for direct communications initiated by the device 106. Incircumstances where the vehicle is using the WiFi Access Point, then theDevice to vehicle connector 120 may use a received SSID and receivedSSID authentication key for validation with the vehicle.

In an example, the device to vehicle protocol negotiator 308 may use acollected server address and access credentials from the server througha cellular data network communications, such as LTE communications, inresponse to an input VIN 302. The device to vehicle protocol negotiator308 may then connect to the vehicle using the WiFi SSID and WiFi.Through this WiFi connection, the device to vehicle protocol negotiator308 may negotiate a Bluetooth out-of-band secure connection followingIEEE 802.11 standards using mutually authenticated transport layersecurity. The device to vehicle protocol negotiator 308 may provide tothe vehicle, a device Bluetooth MAC Address, Srand, a 1280 bit TemporaryKey (TK), and a Pairing Request Command. The device to vehicle protocolnegotiator 308 may receive and process from the vehicle, a BT MACAddress, a 1280 bit TK, a Pairing Response Command, and Mrand. Using thereceived information from the vehicle, the device to vehicle protocolnegotiator 308 may calculate Sconfirm. The device to vehicle protocolnegotiator 308 may receive Mconfirm from the vehicle and separatelycalculate Mconfirm and use this calculated value to confirm a valuematch with the received Mconfirm. The device to vehicle protocolnegotiator 308 may also provide Sconfirm to the vehicle in order toallow confirmation by the vehicle. In an example, if the receivedMconfirm and the calculated Mconfirm values match, then the device tovehicle protocol negotiator 308 may confirm secure pairingcommunications with the vehicle. This process as discussed for both thevehicle and the device follow one example of a secure pairingcommunication protocol, however other pairing protocols are contemplatedthat make use of access information received or learned over a networkcommunication separate from the pairing communications. In variousalternatives, the negotiation of a device to vehicle protocol negotiator308 can use Secure Bluetooth (BT) Classic Out of Band (OOB) pairingprotocols, Secure Bluetooth Low Energy (BLE) OOB Pairing protocols,Legacy BLE OOB pairing, or any other suitable device to deviceprotocols.

In another example, a vehicle and device may authenticate each other forpairing communication prior to being within pairing communication range.When the device 106 is a further physical distance from the pairingcommunications with the vehicle, the device to vehicle protocolnegotiator 308 may also attempt to authorize and validate pairingcommunications through a network communication path. In this example,the device to vehicle protocol negotiator 308 may provide to thevehicle, a device Bluetooth MAC Address, Srand, a 128□bit Temporary Key(TK), and a Pairing Request Command through network communications and aserver. The device to vehicle protocol negotiator 308 may receive fromthe network communications, a BT MAC Address, a 128□bit TK, a PairingResponse Command, and Mrand originating from the vehicle. Using thereceived information from network communications from the vehicle, thedevice to vehicle protocol negotiator 308 may calculate Sconfirm. Thedevice to vehicle protocol negotiator 308 may receive Mconfirm from thevehicle through the server and network communications and thenseparately calculate Mconfirm and use this calculated value to confirm avalue match with the received Mconfirm. The device to vehicle protocolnegotiator 308 may also provide Sconfirm to the vehicle through theserver in order to allow confirmation by the vehicle. In an example, ifthe received Mconfirm and the calculated Mconfirm values match, then thedevice to vehicle protocol negotiator 308 may confirm secure pairingcommunications with the vehicle. In response to a value match betweenthe received and calculated Sconfirm values, the device to vehicleprotocol negotiator 308 may complete the authorization for pairing forsecure communication between the device and the vehicle that will becomeactive when the device enters a physical proximity that enables pairingcommunication.

FIG. 4 is a process flow diagram of an example method 400 for pairing adevice and a vehicle using a network connection. At block 402, a servermay identify a vehicle identification number (VIN) and connectioninformation, wherein the VIN stored in a memory device that links theVIN with the connection information. As used herein the VIN may becomposed of 17 characters digits and letters that act as a uniqueidentifier for the vehicle. In another example, the VIN may be a writtenor digital indicator of a unique vehicle. While the term ‘number’ is inthe acronym, any type of character or identifier that can be stored andmanipulated by a computer system may be used. The identified VIN andconnection information may have been sent to the server, received by theserver, scanned and located in a file system by a processor in theserver. The identification of a VIN can include a receipt of a digitalfile from a manufacturer of the vehicle. In an example, the connectioninformation is a service set identifier (SSID) and an SSIDauthentication key for a communication hardware installed in thevehicle.

A network adaptor may be a hardware device to enable internet or otherwireless communications, where the adaptor may be associated with aspecific ID and password. In an example, the SSID and SSIDauthentication key may be linked to the VIN at a vehicle manufacturer orvehicle assembly location. The network adaptor or other wirelesscommunication device may digitally connect to a vehicle informationhardware device in order to provide and receive information identifyingthe vehicle as well as providing the computers of the vehicle the SSIDand SSID authentication key. In an example, the connection informationfollows the Institute of Electrical and Electronics Engineers (IEEE)802.11 communication standard. This can include the device and vehiclecommunicating with one another directly using the IEEE 802.11 standard.In an example, this can include initial secure connections beingestablished using the standardized four-way handshake between an accesspoint and a wireless client. In an example, the device can be thewireless client and the vehicle can act as the access point. In anexample, the device can act as the access point and the vehicle can actas the wireless client.

In an example, the connection information follows Long-Term Evolution(LTE), where the term ‘Long Term Evolution’ a registered trademark ownedby the European Telecommunications Standards Institute for the wirelessdata communications technology. In example; the connection informationfollows Bluetooth communication protocol, where the term ‘Bluetooth’ isa registered trademark maintained by Bluetooth Special Interest Group.As used herein, Bluetooth is a wireless technology standard forexchanging data over short distances using short-wavelength radio wavesin the radio band from 2.4 to 2.485 GHz from fixed and mobile devices,and building personal area networks (PANs).

At block 404, there is an attempt to match a supplied VIN from aconnecting device with the VIN stored in the memory device. In anexample, the connecting device is a smartphone, tablet, smart watch,headset, augmented reality device, headset wearable, keychain carstarter, credit card, radio frequency ID (RFID) chip, or any othersuitable hardware that a user may commonly carry with them or bring intothe vehicle with them. The supplied VIN can be supplied from anapplication on operating on the connecting device. In an example, thesupplied VIN can be supplied from an application with a manufacturerauthorization which can be done through a separately credentialedservice, can be set up by the manufacturer upon the time of purchase bya user. In an example, the supplied VIN can be provided to a serverdevice in response to a user inputting the VIN, a key, or both.

At block 406, the connection information is sent to the connectingdevice in response to the supplied VIN matching the VIN stored in thememory device, wherein the connection information connects theconnecting device to the vehicle without an intermediate processorbetween the connecting device and the vehicle. In an example, theconnection information can be sent in response to an additionaldetection that the connecting device is within the vehicle, within acertain proximity of the vehicle, within 10 feet of the outside of thevehicle, within a distance that a communication signal from the vehiclecan reach the connecting device, within a distance that both thecommunicating device and the vehicle can exchange information, or anyother suitable distance.

In an example, the VIN stored in the memory and the connectioninformation is removed from the memory in response to a threshold numberof VIN matches have been identified. In an example, after one, two,five, ten, or more matches have been identified and the connectioninformation sent to the devices, no further matches may be permitted. Inan example, the VIN stored in the memory and the connection informationis removed from the memory in response to the elapsing of a thresholdtime duration since the original storing of the VIN number andconnection information in the memory. In an example, the time durationcan be a week, a month, 30 days, or a year since the original storing ofthe VIN number and connection information in the memory of a serverdevice.

FIG. 5 is a block diagram of an example computer-readable medium 500storing instructions, that when executed on a processor pairs a deviceand a vehicle using a network connection. The tangible, non-transitory,computer-readable medium 500 includes instructions that, when executedby a processor 502 can direct the processor 502 through a bus 504 topair a device and a vehicle using a network connection.

The computer-readable medium 500 includes instructions that whenexecuted on a processor employ a VIN storer 506 to store a vehicleidentification number (VIN) and connection information in thecomputer-readable medium 500, wherein the memory device associates theVIN with the connection information and a request with the VIN returnsthe connection information.

The computer-readable medium 500 can include a VIN matcher 508 toattempt to match a supplied VIN from a connecting device through anetwork connection to the computer-readable medium 500, where thematching is attempted between the supplied VIN and the VIN stored in thecomputer-readable medium 500. In an example, the connection informationis a service set identifier (SSID) and an SSID authentication key. In anexample, the connection information follows IEEE 802.11 communicationstandards, Long-Term Evolution (LTE) communication standards, orBluetooth communication protocol as discussed above.

The computer-readable medium 500 can include a server device networkconnector 510 to send the connection information to the connectingdevice in response to the supplied VIN matching the VIN stored in thecomputer-readable medium 500. In an example, the connection informationsent connects the connecting device to the vehicle without anintermediate server between the connecting device and the vehicle. In anexample the computer-readable medium 500 can act to remove the VINstored in the memory and the connection information from the memory inresponse to a threshold number of VIN matches have been identified. TheVIN stored in the memory and the connection information can also beremoved from the memory in response to the elapsing of a threshold timeduration since the original storing of the VIN number and connectioninformation in the memory. In an example, the connecting device is asmartphone, tablet, smart watch, headset, augmented reality device,headset wearable, keychain car starter, credit card, radio frequency ID(RFID) chip, or any other suitable hardware that a user may commonlycarry with them or bring into the vehicle with them.

What is claimed is:
 1. A server device for pairing a connecting deviceand vehicle using a network connection, comprising: a memory to storedata and instructions; a processor, a vehicle identification number(VIN) stored in the memory, where the VIN is associated with connectioninformation for a vehicle associated with the VIN; a VIN matcher storedin the memory that when executed by the processor denies a request forconnection information in response to a mismatch between a supplied VINfrom a connecting device and the VIN stored in memory; and a serverdevice network connector stored in the memory that when executed by theprocessor sends the connection information to a connecting device inresponse to a match between the supplied VIN from the connecting deviceand the VIN stored in memory, the connection information sent through anetwork connection using a first communication protocol and containinginformation for the connecting device to connect to the vehicle througha direct pairing using a second communication protocol.
 2. The serverdevice of claim 1, wherein the connection information is a service setidentifier (SSID) and an SSID authentication key.
 3. The server deviceof claim 1, wherein the first communication protocol follows IEEE 802.11communication standards.
 4. The server device of claim 1, wherein thefirst communication protocol follows Long-Term Evolution (LTE)communication standards.
 5. The server device of claim 1, wherein thesecond communication protocol follows IEEE 802.11 communicationstandards.
 6. The server device of claim 1, wherein the secondcommunication protocol follows Long-Term Evolution (LTE) communicationstandards.
 7. The server device of claim 1, wherein the secondcommunication protocol is a Bluetooth communication protocol.
 8. Theserver device of claim 1, wherein the VIN stored in the memory and theconnection information is removed from the memory in response to athreshold number of VIN matches have been identified.
 9. The serverdevice of claim 1, wherein the VIN stored in the memory and theconnection information is removed from the memory in response to theelapsing of a threshold time duration since the original storing of theVIN number and connection information in the memory.
 10. The serverdevice of claim 1, wherein the connecting device is a smartphone.
 11. Amethod for pairing a connecting device and vehicle using a networkconnection comprising: identifying a vehicle identification number (VIN)and connection information, wherein the VIN stored in a memory devicethat links the VIN with the connection information; attempting to matcha supplied VIN from a connecting device with the VIN stored in thememory device; and sending the connection information to the connectingdevice in response to the supplied VIN matching the VIN stored in thememory device, wherein the connection information connects theconnecting device to the vehicle through a direct pairing.
 12. Themethod of claim 11, wherein the connection information is a service setidentifier (SSID) and an SSID authentication key.
 13. The method ofclaim 11, wherein the connection information follows IEEE 802.11communication standards.
 14. The method of claim 11, wherein theconnection information follows Long-Term Evolution (LTE) communicationstandards.
 15. The method of claim 11, wherein the connectioninformation follows Bluetooth communication protocol.
 16. The method ofclaim 11, wherein the VIN stored in the memory and the connectioninformation is removed from the memory in response to a threshold numberof VIN matches have been identified.
 17. The method of claim 11, whereinthe VIN stored in the memory and the connection information is removedfrom the memory in response to the elapsing of a threshold time durationsince the original storing of the VIN number and connection informationin the memory.
 18. The method of claim 11, wherein the connecting deviceis a smartphone.
 19. A tangible, non-transitory, computer-readablemedium comprising instructions that, when executed by a processor, pairsa device and a vehicle using a network connection, the instructions todirect the processor to: store a vehicle identification number (VIN) andconnection information in the computer-readable medium, wherein thememory device associates the VIN with the connection information and arequest with the VIN returns the connection information; attempt tomatch a supplied VIN from a connecting device through a networkconnection to the computer-readable medium, where the matching isattempted between the supplied VIN and the VIN stored in thecomputer-readable medium; and send the connection information to theconnecting device in response to the supplied VIN matching the VINstored in the computer-readable medium, wherein the connectioninformation sent connects the connecting device to the vehicle through adirect pairing.
 20. The computer-readable medium of claim 19, whereinthe connection information is a service set identifier (SSID) and anSSID authentication key.
 21. The computer-readable medium of claim 19,wherein the connection information follows IEEE 802.11 communicationstandards.
 22. The computer-readable medium of claim 19, wherein theconnection information follows Long-Term Evolution (LTE) communicationstandards.
 23. The computer-readable medium of claim 19, wherein theconnection information follows Bluetooth communication protocol.
 24. Thecomputer-readable medium of claim 19, comprising instructions that whenexecuted on the processor removes the VIN stored in the memory and theconnection information from the memory in response to a threshold numberof VIN matches have been identified.
 25. The computer-readable medium ofclaim 19, comprising instructions that when executed on the processorremoves the VIN stored in the memory and the connection information fromthe memory in response to the elapsing of a threshold time durationsince the original storing of the VIN number and connection informationin the memory.
 26. The method of claim 11, wherein the connecting deviceis a smartphone.